Skip to content

wit: normalize every package to 0.1.0#429

Merged
mfw78 merged 1 commit into
dev/m1from
feat/wit-normalize-0-1-0
Jul 20, 2026
Merged

wit: normalize every package to 0.1.0#429
mfw78 merged 1 commit into
dev/m1from
feat/wit-normalize-0-1-0

Conversation

@mfw78

@mfw78 mfw78 commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

What

Resets every WIT package version and use ... @<ver> reference to a single @0.1.0 across nexum:host and shepherd:cow (the videre:* packages were already @0.1.0 post-rename). Deletes docs/migration/0.1-to-0.2.md and the "Migration from 0.1" section in docs/08-platform-generalisation.md, plus the now-dead cross-links to it in docs 00, 01, 02, 04, 05, 07, the ADRs, sdk.md, and diagrams.md.

Why

The @0.2.0 strings were pre-release cruft, not a real compatibility boundary, and no external consumer pins them. After this cut each package versions independently, so the shared baseline needs to be a clean @0.1.0.

Testing

cargo check / cargo clippy --workspace --all-features (nix develop).

AI Assistance

Drafted with AI assistance under human review.

Closes #371

@mfw78 mfw78 linked an issue Jul 16, 2026 that may be closed by this pull request

@lgahdl lgahdl left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The @0.2.0 -> @0.1.0 version-string sweep itself is complete and clean — checked every .wit file and Rust string literal referencing a WIT import path repo-wide, no stragglers.

The migration-doc link cleanup is incomplete, though, in the same way #344 was: docs/05-sdk-design.md still has 4 dangling inline links to migration/0.1-to-0.2.md that this PR doesn't touch (the diff only removes the one reference-list bullet around line 304-309):

  • docs/05-sdk-design.md:296[migration guide §7](migration/0.1-to-0.2.md#7-sdk-changes-author)
  • docs/05-sdk-design.md:436[migration guide §2](migration/0.1-to-0.2.md#2-error-model-unification-both)
  • docs/05-sdk-design.md:608[migration guide §2](migration/0.1-to-0.2.md#2-error-model-unification-both)
  • docs/05-sdk-design.md:961[migration guide §10](migration/0.1-to-0.2.md#10-deprecation-policy-going-forward-both)

Since this PR deletes the target file, all four will 404 post-merge. Everything else claimed as cleaned up (docs 00, 01, 02, 04, 07, 08, ADR-0001, sdk.md, diagrams.md) checked out fully clean — structurally sound removals, no orphaned headers or broken markdown. Worth a quick follow-up on just these 4 lines before merging.

@mfw78
mfw78 force-pushed the feat/videre-rename-reshape branch from cdda2ba to 6e8371a Compare July 20, 2026 03:45
Base automatically changed from feat/videre-rename-reshape to dev/m1 July 20, 2026 04:32
Reset nexum:host and shepherd:cow package and use versions to 0.1.0,
the shared baseline every package now semvers from independently.
wasi:* keeps its own 0.2.x. Drop the 0.1-to-0.2 migration guide and
its references.

Closes #371
@mfw78
mfw78 force-pushed the feat/wit-normalize-0-1-0 branch from 2943848 to 0e79f7b Compare July 20, 2026 04:34
@mfw78

mfw78 commented Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

On the version sweep: confirmed clean, thanks.

On the migration-doc links: resolved at HEAD, not a live issue on this branch. The four inline links you cited are develop-state, where the target file also still exists, so they are not broken there. On dev/m1 (this PR's base, well ahead of develop) those four inline links were already removed by #245 (558e627, the doc-05 rewrite). This PR (2943848) removes the sole remaining reference (the doc-index bullet at line 307) and deletes docs/migration/0.1-to-0.2.md itself.

Verified end to end: docs/05-sdk-design.md has zero references to migration/0.1-to-0.2.md at this PR's head and through to the last car of the train, so nothing 404s post-merge. No follow-up needed.

@lgahdl lgahdl left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-posting as an inline comment (my earlier review body-only comment didn't render in the diff view).

Comment thread docs/05-sdk-design.md
return.
- [Migration guide §7](migration/0.1-to-0.2.md#7-sdk-changes-author) -
what changed in the SDK surface between 0.1 and 0.2.
- [doc 07](07-rpc-namespace-design.md) - the `chain` RPC passthrough

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The @0.2.0 -> @0.1.0 version-string sweep itself is complete and clean — checked every .wit file and Rust string literal referencing a WIT import path repo-wide, no stragglers.

The migration-doc link cleanup is incomplete, though, in the same way #344 was: this file still has 4 dangling inline links to migration/0.1-to-0.2.md that this diff doesn't touch (the diff only removes the one reference-list bullet just above this line):

  • docs/05-sdk-design.md:296[migration guide §7](migration/0.1-to-0.2.md#7-sdk-changes-author)
  • docs/05-sdk-design.md:436[migration guide §2](migration/0.1-to-0.2.md#2-error-model-unification-both)
  • docs/05-sdk-design.md:608[migration guide §2](migration/0.1-to-0.2.md#2-error-model-unification-both)
  • docs/05-sdk-design.md:961[migration guide §10](migration/0.1-to-0.2.md#10-deprecation-policy-going-forward-both)

Since this PR deletes the target file, all four will 404 post-merge. Everything else claimed as cleaned up (docs 00, 01, 02, 04, 07, 08, ADR-0001, sdk.md, diagrams.md) checked out fully clean — structurally sound removals, no orphaned headers or broken markdown. Worth a quick follow-up on just these 4 lines before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

wit: normalize every package to a single 0.1.0

2 participants